Method and apparatus of performing remote management of a managed machine

ABSTRACT

Disclosed are an apparatus and method of remotely communicating with a managed machine. One example method of operation may include identifying the managed machine operating in a communication network, and transmitting a connection establishment message to the managed machine over the communication network. The method may also include receiving an acceptance message from the managed machine, requesting an administrative service of the managed machine, initiating the administrative service on the managed machine, and forwarding received commands to the administrative service. Such a procedure provides an administrator with the capability to access, modify, update, etc., administrative services operating on a remotely managed machine.

TECHNICAL FIELD OF THE INVENTION

This invention relates to a method and apparatus of accessing a remotely managed machine via an administrator machine, and more specifically, establishing a connection and performing administrative functions to the managed machine over a remote connection.

BACKGROUND OF THE INVENTION

User workstations or managed machines (computing devices) operate in a data communication network by communicating with other managed machines and/or administrator machines. Regardless of the status of the machine, the administrator machines operate to support ongoing communications and applications operating on the managed machines.

Accessing and executing commands on a managed machine through an administrative interface is a common method of updating, controlling, debugging and ensuring the continued seamless operation of the managed machine. However, certain challenges are presented with the advent of varying operating systems, control interfaces and other commonalities of the managed machines operating on a data communication network. For example, various applications used by administrators to manage network computing devices often rely on a web-based browser application to engage the administrator with certain options and simple execution of administrative actions. In addition, feedback communications between the administrator machine and the managed machine(s) may require a secure connection and other communication features prior to authorizing administrative access to managed machines.

SUMMARY OF THE INVENTION

One embodiment of the present invention may include a method of remotely communicating with a managed machine. The method may include identifying the managed machine operating in a communication network, transmitting a connection establishment message to the managed machine over the communication network, receiving an acceptance message from the managed machine, and requesting an administrative service of the managed machine. The method may also include initiating the administrative service on the managed machine, and forwarding received commands to the administrative service.

Another example embodiment of the present invention may include an apparatus configured to remotely communicate with a managed machine. The apparatus may include a processor configured to identify the managed machine operating in a communication network, and a transmitter configured to transmit a connection establishment message to the managed machine over the communication network. The apparatus may also include a receiver configured to receive an acceptance message from the managed machine. The processor may be further configured to request an administrative service of the managed machine, initiate the administrative service on the managed machine, and forward received commands to the administrative service.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B illustrate example network configurations, according to example embodiments of the present invention.

FIG. 2 illustrates an example application communication session, according to an example method of operation of the present invention.

FIG. 3A illustrates an example system diagram of a communication procedure, according to an example method of operation of the present invention.

FIG. 3B illustrates another example system diagram of a communication procedure, according to another example method of operation of the present invention.

FIG. 4 illustrates an example system diagram of a messaging protocol stack, according to an example embodiment of the present invention.

FIG. 5A illustrates a flow diagram of an example method according to an example embodiment of the present invention.

FIG. 5B illustrates a flow diagram of an example method according to an example embodiment of the present invention.

FIG. 6 illustrates an example network entity device configured to store instructions, software, and corresponding hardware for executing the same, according to example embodiments of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

It will be readily understood that the components of the present invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of a method, apparatus, and system, as represented in the attached figures, is not intended to limit the scope of the invention as claimed, but is merely representative of selected embodiments of the invention.

The features, structures, or characteristics of the invention described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments”, “some embodiments”, or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments”, or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In addition, while the term “message” has been used in the description of embodiments of the present invention, the invention may be applied to many types of network data, such as, packet, frame, datagram, etc. For purposes of this invention, the term “message” also includes packet, frame, datagram, and any equivalents thereof. Furthermore, while certain types of messages and signaling are depicted in exemplary embodiments of the invention, the invention is not limited to a certain type of message, and the invention is not limited to a certain type of signaling.

According to example embodiments of the present invention, an administrator may be any information technology (IT) systems administrator, IT service provider, and/or computer owner/operator who provides administrative functions to the computer devices, communication based connections and other network resources. A managed machine may be any network-connected computer device managed by the administrator. The managed machines may be connected directly to the administrator's machine, or, over a remote network connection.

An administrator application may be a web-based application that permits the administrator to manage one or more remote managed machines. A secure network channel may be setup and established between the administrator machine and the remote managed machine via the administrator application. The secure network channel may provide connections over which data packets may be exchanged. The network channel may pass through a wide area network (WAN) (e.g. the Internet) or through a private local area network (LAN).

A server process may be an application that includes a process running on the remote managed machine. The server process accepts connections from the administrator application and assists with setting up a channel and transmitting and receiving commands and data. An administrator plug-in may be a browser plug-in operating in the context of the administrator application that connects with and interacts with the server process of the managed machine over the existing network channel.

FIG. 1A illustrates an example network communication path between a managed machine and an administrator machine, according to example embodiments of the present invention. Referring to FIG. 1A, an administrator machine 102 is in communication with a managed machine 103. The communication path between the machines may be provided over a WAN, such as the Internet, or a LAN. The administrator machine 102 may be a server, computer or other computing device capable of providing a user interface to the administrator. The managed machine 103 may be a laptop, computer, personal digital assistant, smart phone or any other computer network compatible device capable of establishing a communication path or secure channel 110 with the administrator machine 102.

FIG. 1B illustrates an example network communication path between a managed machine 103 and administrator machine 102 that includes an established secure channel 100, according to example embodiments of the present invention. Referring to FIG. 1B, the administrator initiates a connection via a secure channel to the remote managed machine 103. The server process running on the managed machine accepts and acknowledges the connection establishment by transferring an acceptance message back to the administrator application. A secure connection may then be established between the managed machine 102 and the administrator machine 102.

One example method of communicating between the administrator machine 102 and the managed machine 103 is described in detail below with reference to FIG. 2. Referring to FIG. 2, the administrator application 221 of the administrator's user interface 220 may include an administrator plug-in 240, which may be executed and run in a web browser of the user interface 220 on the administrator machine 102. The web browser may establish a connection through a proprietary secure channel 110 to a server process 231 running on the application desktop 230 of the managed machine 103.

In operation, the administrator 102 browses for a particular managed machine 103 viewable from the administrator application 221. The administrator plug-in 240 initiates a connection via a secure channel to a server process 231 of the remote managed machine 103. The server process 231 running on the managed machine accepts and acknowledges the connection establishment by transferring an acceptance message back to the administrator application 221. After session establishment, the administrator may receive a notification or web browser-based indicator that certain commands may be received by the managed machine 103. The administrator may then launch a process to be executed on the managed machine 103.

FIG. 3A illustrates an example system diagram of establishing a connection and performing a service process on the managed machine, according to an example embodiment. Referring to FIG. 3A, like reference numerals refer to like components illustrated in other drawings. The administrator 260 interfaces with the administrator machine 102 to access a web browser 250 linked to an administrator application 245. The administrator 260 may communicate across a network 200 to a remotely managed machine 103. The server process 231 may be executed on the managed machine 103 and may be linked to an administrative service 234. Generally, the managed machine 103 may be operated and controlled by a user.

In response to the administrator's communication input, the administrator application 245 running in the browser 250 of the administrator machine 102, connects over the network 200 to the remotely managed machine 103. Once a connection is established, the administrator application 245 may access administrative management functions operating on the managed machine 103. The managed machine 103 may expose administrative and management functions as types of services that may be managed by the administrator 260. The administrator application 245 running in the browser 250 may access these functions remotely via request and response messages, which are exchanged over the network 200 in a JavaScript object notation message (JSON) format.

According to example embodiments of the present invention, the service operations may be provided to the administrator remotely in the context of a remote management session that is established to perform the service operations (e.g., registry editing, task management, file browsing/transfers, etc.). The service operation messages and their corresponding responses are encoded as JavaScript object notation messages (JSON), which are used to represent simple data structures and associative arrays or objects. JSON is language-independent and uses parsing which provides interoperability of different programming languages and their corresponding operating environments. The JSON messages are created and sent over transmission control protocol (TCP) using a relayed or P2P connection. The messages are exchanged over an existing channel established by an agent, server, and/or browser application.

According to one example embodiment of the present invention, an example communication procedure between the administrator machine 102 and the managed machine 103 is discussed in detail below. The communications begin when the administrator application 245 sends a ‘request for service’ formulated as a JSON message to a remote managed machine 103. The JSON message is delivered over an existing (previously established) secure and reliable communication channel 110 between the browser application of the administrator machine 102 and the managed machine 103. The managed machine 103 receives the service request, identifies the appropriate service, and then acknowledges the service request by transmitting an acknowledgement message to the administrator machine 103.

Upon receipt of the acknowledgement, the administrator application 245 may then deliver administrative commands to the managed machine 103 and initiate requests for content from the service on the managed machine 103. Examples of administrative commands may include start and stop service commands, directory listing retrieval commands, etc. The request/response based interactions between the administrator 102 and the managed machine 103 may all be formatted as JSON messages and delivered over the existing secure communication channel 110.

According to one example embodiment of the present invention, the administrator application 245 transmits a request for a specific administrative service 234 (e.g., registry editing, tasks management, file browsing/transfers, etc.) on the managed machine 103. In response, a service host application on the managed machine 103 receives the application's service request and begins the requested service. The administrator application 245 then sends commands (e.g. obtain directory listing) to the administrative service 234 based on input from the administrator 260. The administrative service 234 receives and processes the commands, and performs the required function (e.g. obtaining and returning a directory listing).

Referring to FIG. 3A, a command prompt client may also be launched within the administrator application 245. Once a connection is established between the administrator machine 102 and the managed machine 103, the command prompt client may cause a command prompt to appear as part of the administrator application 245. The commands entered on the administrative application 245 may be seamlessly executed on the managed machine 103 in real-time. The command prompt client of the administrative application 245 may request a connection to the managed machine 103. As a result of the request, the server process 231 may load the command prompt client of the administrative application 245 and hand-over a command prompt communication service to the administrative service 234 of the managed machine 103. The previously established secure connection may provide a seamless transfer of command prompt commands to be entered at the administrator machine 102 and executed on the managed machine 103.

According to another example embodiment of the present invention, FIG. 3B illustrates another example of an administrative management setup configuration to manage a managed machine. Referring to FIG. 3B, an application service 286 may be a software application that is run on the managed machine 103 that exposes system/administrative functions of the managed machine 103 to remote clients, such as administrator machines 102 that are connected to the managed machine 103 over the network. Some examples of system/administrative functions may include browsing/editing of the Windows Registry, reading performance counters, stopping/starting services, reading the Windows Event Logs, etc.

The application client 282 may also be a software application that is run on the administrator machine 102 that connects and consumes the functions provided by an application service 286 running on a remote managed machine 103. The client software may be hosted in a web browser. The host service 284 may be a software application that is run on the managed machine 103. The host service 284 receives requests for one or more application services 286 from application client 282. The requests initiate the application services on behalf of the clients, and yields to the application service 286 to handle continued interactions with the application client 282.

In operation, the administrator application 280 is used by the administrator 260 to select a particular managed machine that they would like to remotely manage. As a result of this selection, the host service 284 is started on the managed machine 103. The host service 284 opens a listening socket, and the application client 282 in the administrator application 280 connects over the network 200 to the host service 284. In this example, there is already a secure network channel between the administrator machine 102 and the managed machine 103. The application client 282 sends an application information message to the host service 284 identifying a particular application service and specifying a session identifier.

The host service 284 receives the application information message request and identifies the requested application service 286. The host service 284 locates and executes a corresponding application service binary that is capable of processing the request. The host service 284 passes the connected socket to the application service and continues to wait for requests from other application clients. The application service 286 now responds to the application client 282 with an application “acceptance” message to complete initialization of the conversation.

The application client 282 and the application service 286 may then exchange any messages according to the functions of the application service and additional requests of the application client 282. The application service 286 will continue to run until the application client 282 closes the network connection. The host service 284 may have brokered additional conversations between other application clients and services from other administrators not shown.

The messages that are exchanged between application clients and the managed machine's application service may be implemented using the JSON messaging protocol. The wire-format includes an 8-byte header that further includes a message identifier and the message length indicator. The header is followed by the JSON message. All network interaction may be performed over an already established and secure network channel, such as a relayed or peer-to-peer connection between the administrator machine 102 and the managed machine 103.

In addition to boot-strapping the conversation between the application client 282 and the application service 286 (as described above), the communications further implement a ‘keep alive’ mechanism that allows the application service 286 to shut itself down when it is no longer needed. This prevents system resources on the managed machine 103 from being unnecessarily committed and wasted.

The ‘keep alive’ timing mechanism may operated by the application client 282 periodically (e.g., every 2 minutes, 1 minute, etc.) sends a ‘keep alive’ message to the application service 286. The application service 286 consumes the ‘keep alive’ message by updating a time-stamp that is measured from the time a last ‘keep alive’ message was received. The application service expects that a ‘keep alive’ message will be sent at regular intervals. If it does not receive one at an expected point in time, it may be assumed that there is a problem with the application client 282, which, in turn causes a preemptive connection termination. If there are no more application client connections/sessions present, the application service will automatically shut down.

One example using the command prompt may include the IT administrator 260 selecting a given managed machine 103 to start a remote session, which results in starting the host service 284 on the managed machine 103 (as described above). The IT administrator 260 opens the command prompt function of the administrator application 280. The command prompt application client 282 connects to the host service 284. The command prompt application client 282 sends an “applicationInfo” message to the host service identifying the command prompt service as the desired application service. The host service finds the binary data corresponding to the command prompt application service binary and loads the binary data.

The command prompt application service responds to the command prompt client with an “acceptance” message to acknowledge that the application information message was received and processed. The command prompt client may now send messages to the command prompt application service which will process the commands accordingly.

The application service 286 may include a software application that is run on the managed machine 103 that exposes the system/administrative functions of the managed machine 103 to remote clients that are connected to the managed machine 103 over the network 200. Some examples of system/administrative functions are browsing/editing of the Windows Registry, reading performance counters, stopping/starting services, reading the Windows Event Logs, etc.

The above-described example service command operations may be performed based on the messaging protocol stack of FIG. 4. Referring to FIG. 4, the administrator machine 102 may include a browser plug-in application 402, an administrative client 404 and a messaging protocol client 406. The managed machine 103 may include a service dynamic linked library (DLL) an administrative service 410 and a messaging protocol server 408. A service host 420 may be used to load and begin the requested service with the administrative service 410.

A messaging protocol may be used to support the interaction between a browser-based application of the administrator machine 102 and a requested service. The messaging protocol is used to establish the connection between the administrative client application 404 and the service, initiate the conversation between the administrator and managed machine, and deliver the application's messages and commands. The application's messages may be serialized in a JSON format for delivery over the underlying network 200. Pre-pended to each message may be a 12-byte header which includes the size of the message (in bytes) and the type of the message, which may be an integer identifier useful for the application.

The messaging protocol may implement the JSON data format as the ‘wire-format’ for messaging. JSON is a “light-weight data-interchange format”, which is used to facilitate an extensible and adaptable object-oriented messaging protocol that has JavaScript support. The messaging protocol also implements a “keep-alive” and “time-out” mechanism employed by the messaging protocol server 408. Keep-alive messages are sent at a regular interval by the messaging protocol and consumed by the server. If the server, administrator machine 102 and/or managed machine 103 does not receive either a keep-alive or application message within a specific time, then it will drop the connection and end the conversation.

A service framework may be built on top of the messaging protocol and used to perform data communications. The service framework is the implementation by which an administrative service operating on the managed machine 103 may expose its services to a browser-based application in the administrative client application 404. Examples of administrative services may include the file manager service, registry editor service, and the task manager service.

An administrative service 410 may include both an application component and service component. The application component is exposed as a browser plug-in 402 in the administrator client application 404. The application component uses the messaging protocol layer (messaging protocol client 406 and messaging protocol server 408) to request and receive messages from the service component over the network 200. The service component is included in a service DLL 412, which implements the server-side of the messaging protocol 408 to receive and process requests from the administrative application client 404. The service DLL is loaded on demand by a service host 420.

The service host 420 is a server running on the managed machine 103. Upon accepting a connection request, the service host 420 reads an “acceptance” message, which is a JSON formatted message that includes a service descriptor, which may be an identification of the service being requested. The service host finds the service DLL 412 corresponding to the service descriptor and then begins the service if it has not already been initiated. Beginning the service includes loading the dynamic library containing the service and creating the service instance via a user interface. The service host 420 then delegates the handling of the application connection to the service instance.

According to example embodiments of the present invention, a browser plug-in 402 (or application-side JavaScript) may dynamically load a service on a remote machine 103 and issue commands to the service via an object message protocol formatted using JSON messaging format. The messages are exchanged over the existing channel 110 established by the agent, browser, relay, or via P2P. Machine management and administrative services may be exposed via a remotely managed machine. These services may be consumed from a web browser via a JSON (JavaScript Object Notation) based object-oriented message protocol.

One example method of remotely managing a managed machine operation is illustrated in the flow diagram of FIG. 5A. Referring to FIG. 5A, the method may include identifying the managed machine operating in a communication network, at operation 502. The method may also include transmitting a connection establishment message to the managed machine over the communication network, at operation 504. The method may also include receiving an acceptance message from the managed machine, at operation 506, and requesting an administrative service of the managed machine, at operation 508. The method may further include initiating the administrative service on the managed machine, at operation 510 and forwarding received commands to the administrative service at operation 512.

One example method of remotely managing a managed machine operation is illustrated in the flow diagram of FIG. 5B. Referring to FIG. 5B, the method may include selecting the managed machine operating in a communication network, at operation 520, transmitting a connection request message to the managed machine and establishing a secure connection between the managed machine and an administrator machine, at operation 522, and responsive to connecting with the managed machine, executing a host service on the managed machine, at operation 524. The method may also provide connecting to the host service over the communication network via an application client operating on the administrator machine, at operation 526.

The operations of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a computer program executed by a processor, or in a combination of the two. A computer program may be embodied on a computer readable medium, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (“ASIC”). In the alternative, the processor and the storage medium may reside as discrete components. For example FIG. 6 illustrates an example network element 600, which may represent any of the above-described network components 102 and 103, etc.

As illustrated in FIG. 6, a memory 610 and a processor 620 may be discrete components of the network entity 600 that are used to execute an application or set of operations. The application may be coded in software in a computer language understood by the processor 620, and stored in a computer readable medium, such as, the memory 610. The computer readable medium may be a non-transitory computer readable medium that includes tangible hardware components in addition to software stored in memory. Furthermore, a software module 630 may be another discrete entity that is part of the network entity 600, and which contains software instructions that may be executed by the processor 620. In addition to the above noted components of the network entity 600, the network entity 600 may also have a transmitter and receiver pair configured to receive and transmit communication signals (not shown).

While preferred embodiments of the present invention have been described, it is to be understood that the embodiments described are illustrative only and the scope of the invention is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto. 

What is claimed is:
 1. A method of remotely communicating with a managed machine, the method comprising: identifying the managed machine operating in a communication network; transmitting a connection establishment message to the managed machine over the communication network; receiving an acceptance message from the managed machine; requesting an administrative service of the managed machine; initiating the administrative service on the managed machine; forwarding received commands to the administrative service, the received commands comprising at least a request for a directory listing of the managed machine; obtaining and returning the directory listing of the managed machine to an administrator machine based on the received commands; and loading a command prompt client and a command prompt communication service on the managed machine enabling commands initiated by the administrative machine to be performed on the managed machine.
 2. The method of claim 1, wherein transmitting a connection establishment message to the managed machine comprises an administrator plug-in application initiating the connection establishment message via a secure channel to a server process executing on the remote managed machine.
 3. The method of claim 2, wherein the transmitted connection establishment message is received at a server process executing on the managed machine.
 4. The method of claim 1, wherein the administrative service is a registry editor service.
 5. The method of claim 1, wherein the administrative service is a file manager service.
 6. The method of claim 1, wherein the administrative service is a task manager service.
 7. The method of claim 1, wherein forwarding commands to the administrative service further comprises: processing the commands based on input received from the administrator machine.
 8. An apparatus configured to remotely communicate with a managed machine, the apparatus comprising: a processor configured to identify the managed machine operating in a communication network; a transmitter configured to transmit a connection establishment message to the managed machine over the communication network; and a receiver configured to receive an acceptance message from the managed machine; wherein the processor is further configured to request an administrative service of the managed machine, initiate the administrative service on the managed machine, and forward received commands to the administrative service, the received commands comprising at least a request for a directory listing of the managed machine, obtain and return the directory listing of the managed machine to an administrator machine based on the received commands, and load a command prompt client and a command prompt communication service on the managed machine enabling commands initiated by the administrative machine to be performed on the managed machine.
 9. The apparatus of claim 8, wherein the connection establishment message is transmitted to the managed machine via an administrator plug-in application configured to initiate the connection establishment message via a secure channel to a server process executing on the remote managed machine.
 10. The apparatus of claim 9, wherein the transmitted connection establishment message is received at a server process executing on the managed machine.
 11. The apparatus of claim 8, wherein the administrative service is a registry editor service.
 12. The apparatus of claim 8, wherein the administrative service is a file manager service.
 13. The apparatus of claim 8, wherein the administrative service is a task manager service.
 14. The apparatus of claim 8, wherein the processor is further configured to process the commands based on input received from an administrator.
 15. A non-transitory computer readable storage medium configured to store instructions that when executed by a processor perform remote communications with a managed machine, the processor being further configured to perform: identifying the managed machine operating in a communication network; transmitting a connection establishment message to the managed machine over the communication network; receiving an acceptance message from the managed machine; requesting an administrative service of the managed machine; initiating the administrative service on the managed machine; forwarding received commands to the administrative service, the received commands comprising at least a request for a directory listing of the managed machine; obtaining a returning the directory listing of the managed machine to an administrator machine based on the received commands; and loading a command prompt client and a command prompt communication service on the managed machine enabling commands initiated by the administrative machine to be performed on the managed machine.
 16. The non-transitory computer readable storage medium of claim 15, wherein transmitting a connection establishment message to the managed machine comprises an administrator plug-in application initiating the connection establishment message via a secure channel to a server process executing on the remote managed machine.
 17. The non-transitory computer readable storage medium of claim 16, wherein the transmitted connection establishment message is received at a server process executing on the managed machine.
 18. The non-transitory computer readable storage medium of claim 15, wherein the administrative service is a registry editor service.
 19. The non-transitory computer readable storage medium of claim 15, wherein the administrative service is a file manager service.
 20. The non-transitory computer readable storage medium of claim 15, wherein the administrative service is a task manager service. 